Methods and systems for accessing stored content

ABSTRACT

Methods and systems are described for storing content. One or more sections of the stored content may be subdivided into user-specific portions and common portions. The user-specific portions may be stored in user-specific storage associated with corresponding accounts of a plurality of user accounts. The common portions may be stored in common storage associated with the plurality of user accounts. User accounts may request access to the stored content. One or more caching criteria may be used to determine whether to cache any common portions of the stored content. Requests for the content may be processed using the common portions stored in the cache storage.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 16/996,608, filed Aug. 18, 2020, which is herebyincorporated by reference in its entirety.

BACKGROUND

A variety of services are available that provide for personalizedconsumption of content. Users may desire to store content from a livechannel for later consumption. However, content may be provided todifferent users in different container formats. The data may be requiredto be stored and accessed according to various security measures. Thus,there is a need for more sophisticated techniques for content storageand access.

SUMMARY

Disclosed herein are techniques for storing and accessing content. Thedisclosed techniques may configure a content system with greaterefficiencies than conventional storing techniques. A content section maybe subdivided in a user-specific portion and a common portion. Differentversions and/or copies of the user-specific portion may be stored incorresponding user-specific storage for different user accounts. Thecommon portion may be stored in common storage. The common storage maybe independent from each of the user-specific storages. If playback of acontent section is requested, then the user-specific portion associatedwith the requesting user account may be recombined with thecorresponding common portion. The combined user-specific portion andcommon portion may be decoded to form the original playable contentsegment.

A user account may request access to the stored content (e.g., a contentitem). The user account may send a request for a content section of thestored content. A first portion may be determined to be stored inuser-specific storage associated with the user account. A second portionmay be determined to be stored in a cache storage or a common storage.The cache storage may store a range (e.g., a rolling window) of secondportions. A range of content sections associated with a content sourcemay be determined for caching based on one or more caching criteria. Theone or more caching criteria may specify a threshold number of useraccounts, a threshold distance between requested content sections of acontent source, and/or the like. Second portions corresponding to therange of content sections may be moved and/or copied to the cachestorage from the common storage. If a requested second portion is in thecache storage, the request may be processed using the cache storage.Otherwise the second portion may be accessed via the common storage. Thesecond portion may be combined with the first portion to determine therequested content section. The combination of the first portion and thesecond portion may be combined with other data (e.g., header data). Thecombination of the first portion and the second portion may be sent to auser device associated with the user account.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments and together with thedescription, serve to explain the principles of the methods and systems.

FIG. 1 is a block diagram showing an example operating environment.

FIG. 2 is a diagram showing example content structure.

FIG. 3A is a diagram showing example content storage.

FIG. 3B is a diagram showing example content storage.

FIG. 3C is a diagram showing example content storage.

FIG. 3D is a diagram showing example content storage.

FIG. 4 is a diagram showing example content storage.

FIG. 5 is a diagram showing example content storage.

FIG. 6 is a diagram showing example content access.

FIG. 7 is a diagram showing example content access.

FIG. 8 is a flow diagram showing an example method.

FIG. 9 is a flow diagram showing an example method.

FIG. 10 is a flow diagram showing an example method.

FIG. 11 is a block diagram illustrating an example computing device.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Disclosed herein are techniques for storing and accessing content. Thedisclosed techniques may configure a content system with greaterefficiencies than conventional storing techniques. A content section(e.g., a content segment) may be subdivided in a user-specific portionand a common portion. Different versions and/or copies of theuser-specific portion may be stored in corresponding user-specificstorage for different user accounts. The common portion may be stored incommon storage. The common storage may be independent from (e.g., orseparate from) each of the user-specific storages. A subsystem used forstoring the common storage may be independent from (e.g., or separatefrom) a subsystem used for user-specific storage. The subsystem used forstoring the common storage may be implemented using different storagethan the storage used for storing the user-specific storages. Ifplayback of a content section is requested, then the user-specificportion associated with the requesting user account may be recombinedwith the corresponding common portion. The combined user-specificportion and common portion may be decoded to form the original playablecontent segment.

In some scenarios, a content section of a content item may be recorded(e.g., or stored) while at the same time, another content section of thecontent item may be requested and/or sent for playback by a user device.This scenario, sometimes referred to as “hot playback” may be taxing ona content storage system, resulting in higher latencies and higherprobability of failures. This may occur for popular live content, suchas competitions, talent shows, sports, and/or the like. For popularshows, the number of unique recordings being written concurrently withunique segments being played back may reach numbers that are heavilytaxing for the content storage system.

An example, non-limiting, scenario may comprise over ten thousandviewers that have associated processes of both recording and playback.If all content sections of the content are recorded uniquely per userwithout the ability to extract any commonality in the video, there maybe massive inefficiencies in the system when those the user accounts areplaying back the content within a relatively short time period to oneanother. If there existed a caching technique that cached commonportions of the content sections, the ten thousand requests to asubsystem could be greatly reduced in both bytes and requests.

Disclosed is a new caching technique for common portions of the storedcontent. The disclosed caching technique may comprise tracking a numberof requests for playback of a section of a content item. A range (e.g.,window, logical window, sliding window, content window, rolling window)corresponding to a subset of the content sections of the content itemmay also be determined. The range may be based on a time system specificto the content item, such as a content stream time. The range mayspecify timing information (e.g., start time, end time, time rangebeginning, time range ending), section information, (e.g., firstsection, last section, section range beginning, section range ending), acombination thereof, and/or the like. Common portions that match therange of content sections may be copied and/or moved to a cache storage.

The range may be determined, created, updated, and/or the like based ona change in a metric indicative of requests for playback. The metric maycomprise a number of requests for playback, a request rate associatedwith requests for playback, and/or the like. The request rate maycomprise a number of requests occurring within a time interval.

By utilizing a range of time and/or a request rate of playback requestsfor the same content item (e.g., or same content source), a cachingrange may be implemented in which user accounts do not have to requestthe same content section to trigger caching of common portions for arange of content sections. Multiple playback requests for commonportions within that range may be served from cache, rather thangenerating individual requests to the common storage subsystem for thesame common portion as previous requests. If the number (e.g., orrequest rate, number within a time interval) of requests does not meet athreshold, caching may not occur at all (e.g., where only a handful ofuser accounts are playing back the same recorded program).

FIG. 1 is a block diagram showing an example system 100 for providingcontent. The system 100 may comprise one or more of a content device102, a storage device 104, and a user device 106. The content device102, the storage device 104, and the user device 106 may becommunicatively coupled via a network 110.

The network 110 may comprise a content distribution and/or accessnetwork. The network 110 may facilitate communication via one or morecommunication protocols. The network 110 may comprise fiber, cable, acombination thereof. The network 110 may comprise wired links, wirelesslinks, a combination thereof, and/or the like. The network 110 maycomprise routers, switches, nodes, gateways, servers, modems, and/or thelike.

The content device 102 may be configured to send content 112 to aplurality of users. The content 112 may comprise video data, audio data,closed caption (CC) data, a combination thereof, and/or the like. Thecontent 112 may comprise a plurality of content channels (e.g., 112 a,112 b, and up to 112 n), such as live channels, streaming channels,cable channels, and/or the like. The content device 102 may comprise oneor more servers. The content device 102 may be one or more edge devicesof a content distribution network and/or content access network. Thecontent device 102 may comprise a transcoder configured to encode,encrypt, compress, and/or the like the content. The content device 102may comprise a packager configured to package the content, segment thecontent, and/or the like. The content device 102 may be configured tomanage recorded content (e.g., schedule recordings, access recordings,etc). The content device 102 may send the content as a plurality ofpackets, such as transport stream packets, Moving Picture Experts Group(MPEG) transport stream packets, and/or the like. The content device 102may send the content 112 to the storage device 104.

The user device 106 may be configured to receive the content 112 fromone or more of the content device 102 or the storage device 104. Theuser device 106 may comprise a computing device, smart device (e.g.,smart glasses, smart watch, smart phone), a mobile device, a tablet, acomputing station, a laptop, a digital streaming device, a set-top box,a streaming stick, a television, and/or the like.

The user device 106 may be configured to receive the content via acommunication unit 114. The communication unit 114 may comprise a modem,network interface, and/or the like configured for communication via thenetwork 110. The user device 106 may comprise a user interface unit 116.The user interface unit 116 may be configured to cause display of a userinterface. The user interface may be configured to allow the user tobrowse available content, such as content sent by the content device102, content stored by the storage device 104, and/or the like. The userinterface may be configured to allow users to request content, such as acontent channel (e.g., or a content asset being supplied via a contentchannel), be stored (e.g., recorded) for later viewing. The userinterface may be configured to cause storage of the content based on aconfiguration setting, such as a buffering setting associated withbuffering content in storage (e.g., if a user begins watching a channel,if a rule is triggered, if the user is predicted to request the contentat a time time).

The storage device 104 may be configured to store content, such ascontent recorded from a content channel, a content asset, and/or thelike. The storage device 104 may store the content for a plurality ofusers. The storage device 104 may comprise a storage service 118configured to store and/or manage storage of the content. The storagedevice 104 may be configured to send the stored content (e.g., afterreconstituting the content) upon requests from the user device 106.

The storage service 118 may be configured to subdivide (e.g.,deconstruct, divide) content into a plurality of portions for storage.Subdividing may include separating data into separate blocks, copying asingle block as multiple separate blocks, and/or the like. The storagedevice 104 may receive the content from the content device 102. Thecontent may be received as a plurality packets, such an internetprotocol packets, transport stream packets, and/or the like. A packetmay comprise one or more sections (e.g., segments, frames, blocks) ofcontent. A section of content may comprise a plurality of frames ofcontent. The storage service 118 may be configured to subdivide asection of content and/or a frame of content into the plurality ofportions. The storage service 118 may be configured to subdivide eachsection of the content into a corresponding plurality of portions of thecontent. The storage service 118 may be configured to subdivide thecontent on a per user basis. The storage service 118 may be configuredto subdivide the content such that the plurality of portions aredifferent or the same for different users (e.g., for the same content).

The storage service 118 may be configured to subdivide content multipletimes. The content may comprise header data and media (e.g., video,audio, bit stream) data. The content may be subdivided into a headerportion comprising the header data and a media portion comprising themedia data. The media portion may be subdivided into a first portion(e.g., a user-specific portion and a second portion (e.g., remainingportion, common portion).

The content (e.g., media portion, or section of the media portion) maycomprise a bit sequence (e.g., an ordered sequence of bit values). Thebit sequence may comprise encoded data, such as an entropy encoded datasequence, a context-adaptive binary arithmetic coding (CABAC) datasequence, a context-based adaptive variable-length coding (CAVLC) datasequence, and/or the like. The bit sequence may comprise encoded contentseparated from header data. The bit sequence may comprise one or moreframes of the content.

The storage service 118 may determine the first portion and/or thesecond (e.g., for a specific section of content). The storage service118 may determine the first portion and/or the second portion using avariety of techniques, such as the techniques shown in FIGS. 3A-D. Thestorage service 118 may determine the first portion and/or the secondportion based on one or more selection rules, such as a predefined rule,a randomization function, and/or the like. The predefined rule may beany rule and/or function for determining the first portion and/or secondportion.

The storage service 118 may determine the first portion based on arandomized selection of bits of the bit sequence. The randomizedselection of bits may be bits matching a randomized data range (e.g., orother criteria, such a list of random numbers corresponding to an indexof the bit sequence). The randomized data range may be generated using arandomization function (e.g., a random number generator, an algorithm orservice that produces a random or pseudo-random number, for example,based on a seed). A random number may be generated and used to determinea number of digits or bits of the sequence that are within the range. Ifthe random number is X, then the randomized data range may comprise thefirst X amount of bits of the bit sequence (e.g., for a frame), the lastX amount of bits of the bit sequence, X number of bits beginning at anoffset (e.g., randomized offset), and/or the like.

The randomization function may be applied (e.g., deterministically, toachieve the same result) for different users. The random number (e.g.,or randomized data range) may be the same for each of a plurality ofusers (e.g., for a specific section of content). The randomizationfunction may result in selection of different first portions and/orsecond portions for different sections of content.

For a first section of content, the first portion may be different thanfor a second portion of content. For purposes of illustration, the mediadata may comprise a first section of 100 bits and a second section of100 bits. It should be understood that a typical bit sequence may bemuch longer (e.g., 160 bytes), but the example is used only for ease ofexplanation. If the storage service 118 determines a randomized datarange of 10 bits for a first section, then the first portion associatedwith the first section may comprise the first 10 bits of the firstsection. The second portion may comprise the last 90 bits of the firstsection. If the storage service 118 determines a randomized data rangeof 15 bits for the second section, then the first portion associatedwith the second section may comprise the first 15 bits of the secondsection. The second portion may comprise the last 85 bits of the secondsection.

The first portion and/or section portion may be determined based on aconstraint (e.g., parameter), such as a size, an amount, a ratio, apercentage, and/or the like associated with a section (e.g., or segment)of content. The constraint may indicate an amount of data (e.g., databits, data blocks, data bytes) in the first portion, such as a minimumamount, maximum amount, range of the amount, and/or the like. Theconstraint may indicate an amount data (e.g., data bits, data blocks,data bytes) in the second portion, such as a minimum amount, maximumamount, range of the amount, and/or the like. The constraint mayindicate an amount data from a section of content to include in thefirst portion and/or an amount data from the section to include in thesecond portion. The constraint may indicate that the first portion mustbe equal to or less than about 10%, about 5%, about 2%, about 1%, and/orthe like of the section of content. The constraint may indicate that thesecond portion must be greater than or equal to about 90%, about 95%,about 98%, about 99%, and/or the like of the section of content. Theconstraint may indicate that the second portion and the first portionmust be in a ratio of about 9 to about 1, about 8 to about 2, about 95to about 5, about 98 to about 2, about 99 to about 1, and/or the like ofthe section of content. The constraint may be an average constraint,such that the first portion and second portion must be determinedaccording to the constraint on average over multiple sections ofcontent.

The constraint may be based on a characteristic of the content, such assize of the content, amount of motion in the content, type of frame inthe content, a combination thereof, and/or the like. The constraint maybe based on a size of a portion of content that a user device isexpected to request. If the user device requests one segment (e.g., a 2second segment comprising 48 frames) at a time, then the constraint maybe based on a size of the segment.

The storage service 118 may store the first portions in user-specificstorage. User-specific storage associated with a first user may comprisefirst user-specific storage 120 (e.g., a first location, first volume,first directory, first file, first grouping of files). User-specificstorage associated with the second user may comprise seconduser-specific storage 122 (e.g., a second location, second volume,second directory, second file, second grouping of files). The firstuser-specific storage 120 may be different than the second user-specificstorage 122. Permissions may be used to restrict users to accessuser-specific storage associated with the corresponding account. Thefirst user-specific storage 120 may be associated with a first account.The second user-specific storage 122 may be associated with a secondaccount. The first account may not have permission to access the seconduser-specific storage 122. The second account may not have permission toaccess the first user-specific storage 120.

The storage service 118 may be configured to store a copy of the firstportion in the first user-specific storage 120. The storage service 118may be configured to store another copy of the first portion in thesecond user-specific storage 122. The copy of the first portion storedin the first user-specific storage 120 may be identical to the copy ofthe first portion in the second user-specific storage 122. The storageservice 118 may be configured to store a copy of the first portion fromthe first section and a copy of the first portion from the secondsection in first user-specific storage 120 and/or the seconduser-specific storage 122.

The storage service 118 may be configured to store the second portion(e.g., or second portions from each section) in common storage 124. Aplurality of second portions (e.g., from different sections of content)may be stored as one file, or as separate files, or a combinationthereof. The second portion may be stored with randomized data.Randomized data (e.g., one or more random bits or bytes) may beprepended, appended, inserted within, and/or the like the secondportion. The second portion (e.g., for each section) may be stored onlyonce for a plurality of users. A second portion (e.g., for a section ofcontent) may be stored in the common storage for a first user account.The same copy of the second portion may also be used (e.g., referenced)for a second user account.

In some scenarios, the content (e.g., a content item) may have one ormore versions of the content. Different versions of the one or moreversions may be associated with (e.g., or sent to, stored for) differentusers. The one or more versions may correspond to different bit rates,encodings, device specific formatting, and/or the like. The one or moreversions may comprise different watermarking data. The differences fromone version of the content to another may be stored in user-specificstorage. The common storage 124 may comprise portions of the one or moreversions of the content that are the same. In addition or in thealternative, the common storage 124 may comprise a plurality of versionsof the content. For a frame, different versions of the frame may bestored in the user-specific storage and/or the common storage 124. Theone or more versions may comprise differences in slice, variations of anarea within a picture, a combination thereof, and/or the like. A portionof content (e.g., a last frame of a set of frames, such as packet offrames) may be modified to generate the one or more versions of thecontent. Randomized bytes may be added to generate the one or moreversions of content, versions of a set of frames, versions of a frame,and/or the like. Different users may access different version of the oneor more versions to determine the content.

The storage service 118 may be configured to generate data fordetermining (e.g., reconstituting) the stored content. The data fordetermining the stored content may comprise an identifier of the firstportion, a location of the first portion, an identifier of the secondportion, a location of the second portion, an ordering of the firstportion and second portion, and/or a combination thereof. The data fordetermining the stored content may comprise an association of the firstportion and the second portion. The data for determining the storedcontent may be stored as a record in an index (e.g., or other datastructure). If a section of content comprises K number of frames, theindex may comprise K records. Each of the K records may comprise datafor determining a corresponding frame of the section.

The data for determining the content (e.g., or frame) may compriseinformation for determining a portion of the content (e.g., the firstportion) stored in user-specific storage, information for determiningthe portion of the frame stored in common storage, and/or the like. Thedata for determining the content may comprise data indicating X bits(e.g., or bytes) from the user-specific storage (e.g., corresponding tothe first portion). The data for determining the content may comprisedata indicating Y bits (e.g., or bytes) from the common storage 124(e.g., corresponding to the second portion). The data for determiningthe content may comprise an association of the X bits and the Y bits(e.g., and instructions for recombining them). The data for determiningthe content may comprise a location, directory, file, bit offset, byteoffset, and/or the like for locating the X bits and/or the Y bits.

The data for determining the content may be stored in the user-specificstorage. The data for determining the content may be stored in an indexfile, a database, a document, a manifest, a data structure (e.g., XML,JSON, HTML), and/or the like. First data for determining the content maybe stored in the first user-specific storage 120. Second data fordetermining the content may be stored in the second user-specificstorage 122. If a request to access the content (e.g., or the frame)associated with the first user account is received, then the first datamay be used to determine (e.g., reconstitute) the content. The firstdata may be accessed based on a user credential associated with thefirst user account. If a request to access the content (e.g., or theframe) associated with the second user account is received, then thesecond data may be used to determine the content. The first data may beaccessed based on a user credential associated with the second useraccount.

The storage service 118 may be configured to process requests for thestored content. The storage service 118 may determine (e.g.,reconstitute) sections of the content in response to requests for thecorresponding sections. The storage service 118 may be configured todetermine the content (e.g., or sections of content) based on the storeddata for determining the content. The content (e.g., or section ofcontent) may be determined by combining the first portion stored inuser-specific storage (e.g., or common storage) and the second portionstored in the common storage 124. The X bytes from the user-specificstorage may be combined with the Y bits from the common storage 124. Thedata structure for reconstituting the frame may be used to determine thespecific data to recombine. The Y bits may be appended to the X bits(e.g., if the user-specific portion is from the beginning of the bitsequence).

The storage service 118 may be configured to locate the data fordetermining the content based on a user account (e.g., associated with arequest for the content). The user account may be associated with aspecific user-specific storage, user-specific storage area, and/or thelike. A database may be used (e.g., by the storage service 118) toassociate user accounts with corresponding user-specific storage. Adatabase may be used (e.g., by the storage service 118) to associateuser accounts with corresponding content recording information. Thecontent recording information may comprise an identifier (e.g., orlocation) of user-specific storage, an identifier for data fordetermining the content, and/or the like. Upon receiving a request, thestorage service 118 may determine (e.g., based on the association) thecorresponding user-specific storage for a user account, the data fordetermining the content, and/or the like. The storage service 118 mayaccess the user-specific storage (e.g., or other location, such as adatabase) to determine the data for determining the content. The datafor determining the content may comprise an index, one or more entriesin an index, and/or the like stored in the user-specific storage. Thedata for determining the content may comprise one or more entries in adatabase that may be determined based on a user account identifier, acontent recording identifier, and/or the like.

The storage service 118 may use the data for determining the content todetermine a location of a first portion of the content. The firstportion of the content may be copied into memory. The storage service118 may use the data for determining the content to determine a locationof the second portion of the content. The second portion may be copiedinto memory and added to (e.g., appended to, combined with) the firstportion to form a section (e.g., segment of content). The section ofcontent may be sent to a user device 106 requesting the content. Therequest may be specific to the section of content. If the user device106 requests a section (e.g., such as a 2 second segment of content) ofcontent, the section of content may be determined and sent to the userdevice 106. The first portion and second portion may be combined as amedia portion (e.g., CABAC encoded data). The media portion may becombined with a header portion (e.g., by appending the media portion tothe end of the header portion). The combined header portion and mediaportion may be sent to the user device 106 (e.g., as a single sectionand/or segment of content). After receiving the requested section, theuser device 106 may request (e.g., using a manifest) the next section ofcontent. The process for determining the next section may then beperformed. In some scenarios, multiple first portions and secondportions (e.g., first portion 1 _(1-n), second portion 1 _(1-n), firstportion 2, second portion 2) may be combined by the storage service 118.The multiple combined portions may be sent to satisfy a request for asection (e.g., segment) of content.

In some scenarios, the content may comprise watermarking data, such asan additional frame that is added to content, an additional set of dataadded to a bit sequence, and/or the like. The watermarking data mayidentify a user account that is accessing and/or requesting the content.The watermarking data may be stored in the user-specific portion. Thedata for determining the content may comprise data indicating thewatermarking data.

The storage service 118 may be configured to implement a cachingservice, such as the caching service described elsewhere herein. Thestorage service 118 may be configured to cause storage (e.g., at leasttemporarily) of one or more second portions (e.g., or second portionsfrom each section) in cache storage 126. Requests for second portionsmay be forwarded to the caching service. If a requested second portionis stored in cache storage 126, then the request may be processed usingthe second portion stored in the cache storage 126. If the secondportion is determined to not be stored in cache storage 126, then therequest can be processed by accessing the second portion stored in thecommon storage 124.

The one or more second portions may be caused to be stored in the cachestorage 126 based on one or more caching criteria. The one or morecaching criteria may be used to determine a range of content sectionsfor caching in the cache storage 126. Content sections from the originalcontent source (e.g., from which the content was recorded/stored) may besequentially numbered (e.g., or otherwise identified). The numbering(e.g., or other identification) may be used to correlate stored (e.g.,or recorded) content sections with corresponding (e.g., matching)content sections of the content source. If a content section from theoriginal content source is used to determine a plurality of firstportions and a corresponding second portion, the second portion can beassociated with (e.g., based on the number or other identification) thecontent section of the original content source.

The range of content sections may be determined based on a thresholdnumber of user accounts requesting to access content sections within athreshold period of time. The threshold number of user accounts cancomprise any number, such as 5, 10, 100, 500, 1000, or any other number.The threshold period of time may comprise any time range, such as a 5second time window, a 10 second time window, a 30 second time window, a1 minute time window, or any other time window. Requests from useraccounts can be tracked over time as one or more metrics. The one ormore metrics may be analyzed and/or otherwise compared to the thresholdnumber of user accounts, the threshold time period, and/or other cachingcriteria. If the one or more caching criteria are satisfied, thencaching information may be determined. The caching information maycomprise a range of content sections, a time to cache the range ofcontent sections, an associated content source, and/or the like. Thecaching information may be used to cause second portions that match thecaching information to be stored in the cache storage 126. The cachinginformation may be updated over time (e.g., or the time to cache mayexpire) to cause the cached content to be updated and/or removed fromthe cache storage 126.

FIG. 2 is a block diagram showing example content. The content maycomprise a media sequence, content sequence, bit sequence, and/or thelike. The content may be divided into a plurality of portions, such asbit segments, byte segments, blocks (e.g., macroblocks), and/or thelike. The content may comprise a plurality of packets, such as mediatransport stream packets. An example packet may comprise headers andadaptation field data.

The content may comprise a plurality of packets, such as transportstream packets, MPEG-2 transport stream packets, and/or the like. Thecontent may be subdivided (e.g., divided, deconstructed, segmented) intoone or more header portions 202 (e.g., a first bit sequence, a firstfile) and one or more media portions 204 (e.g., second bit sequence, asecond file, non-header portion). A header portion 202 may compriseheader data, adaption field data, and/or the like. A media portion 204may comprise the data that remains after removing some or all of theheaders. The media portion 204 may comprise media data. The media datamay comprise one or more sections, segments, frames, blocks, and/or thelike. The media data may be subdivided into one or more first portions(e.g., stored in user-specific storage) and one or more second portions(e.g., stored in common storage).

An example header portion 202 may comprise container/systems-specificdata. The header portion 202 may comprise header data. The headerportion 202 may comprise one or more headers for decoding the content.Several example headers are shown in FIG. 2 for purposes ofillustration, but it should be understood that other headers may beused. For MPEG-2 TS, the header portion 202 may comprise systemsmetadata such as PAT, PMT, CAT, SCTE 35, EBIF, and/or the like. Theheader portion 202 may comprise one or more PES headers. For ISO-BMFF,the header portion 202 may comprise one or more (or all) ISO-BMFF boxesfrom the beginning of each fragment within the media file (e.g., startof ‘ftyp’ or ‘styp’ boxes) and till the end of the header of the ‘mdat’box (e.g., till the first byte of the bitstream). For H.264 and H.265video, the header portion 202 may comprise one or more (or all) non-VCLNAL units, one or more (or all) NAL headers of non-VCL NAL units, and/orthe like. The header portion 202 may comprise slice headers of NAL unitscomprising slices.

The media portion 204 may comprise image data, video data, audio data,and/or the like. The media portion 204 may comprise bitstream data. Themedia portion 204 may comprise CABAC-coded data in case of H.264 andH.265. The media portion 204 may comprise a pixel-specific data, such asa pixel-specific sequence bitstream.

The process of deconstructing, subdividing, and/or the like of contentdescribed herein may be applied to non-NAL data, non-video media, audiodata, and/or the like. For (E-)AC-3 the syncframe( ) and bsi( )syntactic elements may be stored in the container-specific storage. Theaudblk( ), auxdata( ), and errorcheck( ) syntactic elements may bedeconstructed into first portions (e.g., for user-specific storage) andsecond portions (e.g., for common storage).

As described in more detail elsewhere herein, the header portion 202 maybe stored in user-specific storage and/or common storage. The headerportion 202 may be stored in container-specific storage. The containerspecific storage may be stored in the user-specific storage, the commonstorage, a combination thereof, or a separate storage. Thecontainer-specific storage may be specific to a type of containerassociated with the content. Data, such as an index, may be stored fordetermining the content based on the header portion 202 and the mediaportion 204. One index may be stored for determining a media portion 204based on first portions and second portions. Another index may be storedfor determining a packet based on a header portion 202 and a mediaportion 204.

As shown in FIGS. 3A-D, the media portion 204 may be subdivided into afirst portion 302 and a second portion 304 in a variety of ways. Thefirst portions 302 and/or the second portions 304 may be stored in asingle file (e.g., as a bit sequence) or multiple separate files. Itshould be understood that regardless of whether the first portions 302are shown as separate or combined, the first portions 302 may be storedas a single file or as multiple files. It should be understood thatregardless of whether the second portions 304 are shown as separate orcombined, the first portions 302 may be stored as a single file or asmultiple files. The first portions 302 may be stored as a single file ona per segment basis (e.g., or per section basis). The second portions304 may be stored as a single file on a per segment basis (e.g., or persection basis). A segment (e.g., or section) may comprise a 2 secondportion of content comprising, for example, 48 frames. Each segment mayhave an associated file (e.g., in user-specific storage) that stores thefirst portions 302. Each segment may have an associated file (e.g., incommon storage) that stores the second portions 304.

FIG. 3A shows an example storing of first portions 302 and secondportions 304. The first portion 302 may be stored in user-specificstorage. The second portion 304 may be stored in common storageassociated with a plurality of user accounts. The first portion 302 maycomprise a portion of a bit sequence. The first portion 302 may bedetermine based on one or more selection rules. The one or moreselection rules may comprise any rule, function, logic, and/or algorithmfor determining (e.g., selecting) portion of content (e.g., a portion ofthe bit sequence). The one or more selection rules may comprise apredefined rule for determining specific bits of the bit sequence. Theone or more selection rules may comprise a randomization function thatrandomly selects content. The one or more selection rules may be applieddeterministically, such that the same portions of content are selectedfor each user. The first portion 302 may be the same for different usersstoring the same content. A randomized sequence of bits may bedetermined using the randomization function to randomly select numbersin a sequence. After the randomized sequence of bits is determined, therandomized sequence of bits may be applied to each user in the samemanner to determine the same user-specific portion for each user.

The one or more selection rules may vary in result for differentportions of the content. The size (e.g., or number of bytes, bits) ofthe first portion 302 may be randomly determined for each of a pluralityof sections of content (e.g., on a per segment, per macroblock, and/orper frame basis). A number of bits of the first portion may be based ona predefined number. A random number, R0, may be added to the predefinednumber to determine a randomized bit range. If the predefined number isX, the first at least X+R0 bytes of a data portion (e.g., of a frame, ofthe media portion 204) may be copied as a first portion 302. The firstportion 302 (e.g., X+R0, which may be media data, such as CABAC codeddata) may be copied into a file (e.g., as block b0 of a file as shown inFIG. 3A) in user-specific storage. The file may comprise other firstportions (e.g., associated with the user) of the content. The file maycomprise only the first portions of the content.

The selection rules (e.g., or randomization function) may comprise arandomization constraint. The randomization constraint may constrainselection of random information (e.g., random numbers, random byteranges, randomized data added to the first portion and/or secondportion). The random information may be constrained to match aprobability distribution. A random number, R1, may be determined. R1bytes of the content may be copied into the user-specific storage asblock b1. Additional blocks of data may be copied into correspondingportions of the user-specific storage and the common storage until thecontent is completely stored (e.g., all frames of the content have beenstored). The random numbers R0 and R1 (e.g., and other randomlydetermined information) may have an associated probability distribution.The probability distribution may be defined to tune the size and/orsecurity of the blocks of data stored in the common portion. The randomnumber may be determined based on the formula R=N+r where r is aGaussian-distributed random number, and Nis a constant.

FIG. 3B shows another example storing of first portions 302 and secondportions 304. The first portions 302 may be determined using the one ormore selection rules (e.g., as in FIG. 3A). The first portions 302 maybe stored in the user-specific storage. The second portions 304 may bestored in the common storage. Additional data may be added to the secondportions 304 and/or common storage (e.g., to cause the stored data to bemore difficult to decode). Random amounts of random bits (e.g., orbytes, shown as Rand( ) may be stored in the common storage (e.g., alongwith the second portions). The random bits may be stored in a sequencebetween one or more second portions 304, before a first one of thesecond portions 304, following a last one of the second portions 304,and/or a combination thereof. One or more of the data blocks (e.g., ofthe second portions 304) copied to the common storage may modified,encoded, and/or the like. A block may be further XOR′ed with a number.The number may be stored in the file in the common storage.

In some scenarios, the stored content may be the same or similar fordifferent users. A first user and a second user may both request tostore the same content (e.g., the same frame of content, same contentasset). If content is being stored in common storage for the first user,the content can be compared to stored content (e.g., prior storedcontent) associated with the second user also stored in the commonstorage. A single content asset may have one file for storing the commonportion for a plurality of different users. A signature associated withthe content (e.g., or a part of the content such as a frame) may becompared to a signature of the content already stored for the seconduser. An example signature may comprise an MD5, SHA-1, SHA-3, and/orother signature. Signatures may be stored (e.g., in a database) for theheader portion (e.g., header data, container-specific portion) and/orthe common portion. The stored signature may be compared to a computedsignature (e.g., computed based on the content associated with the firstuser). A signature associated with the header portion may be compared toone or more stored signatures. If an identical signature is not found,the content may be stored. In some scenarios, the content stored fordifferent users may be the same. A header for one user may be the sameas a header for another user. The content associated with the header maydiffer for different users according to formatting (e.g., containerformatting), device content requirements, and/or the like.

The user-specific storage may comprise one or more files associated withthe content. The user-specific storage may comprise metadata on thestored content (e.g., media sequence). The user-specific storage maycomprise blocks containing user-specific bytes. The user-specificstorage may comprise instructions for determining the content (e.g., amedia sequence, section) from the combination of the first portion(e.g., container-specific portion) and the second portion (e.g.,user-specific portion, the common portion).

If a user requests access to the content, the content may be determined(e.g., reconstructed) using the first portions 302 and the secondportions 304. The instructions for determining the content may comprisean indication and/or location of a first portion 302. The instructionsmay comprise an indication and/or location of a second portion 304. Theinstructions may comprise an ordering of the first portion 302 and thesecond portion 304. The instructions may comprise one or moreindications to skip the additional data. The instructions may comprise afirst instruction (e.g., access X bytes starting at location B in a bitsequence) to access the first portion 302 in the user-specific storage,a second instruction (e.g., skip Y bytes starting at location R in afile in common storage) to skip the additional data stored in the commonstorage, a third instruction (e.g., access Z bytes starting at locationM in a bit sequence) to access the second portion 304 in the commonstorage, and/or a combination thereof. The second instruction may beordered (e.g., in an index) after the first instruction. The thirdinstruction may be ordered after first instruction and the secondinstruction. The content, such a section (e.g., or segment, 2 secondsegment), may be reconstituted by following the first instruction, thesecond instruction, and/or the third instructions. In someimplementations, the second instructions may be omitted (e.g., becauseaccessing the location of the second portion 304 results in skipping theadditional data). The content may be reconstituted by a server deviceand/or a user device.

FIG. 3C shows another example of storing of first portions 302 andsecond portions 304. The content may be stored using watermarking orsimilar techniques. For a particular content item (e.g., contentstream), the content item may be encoded as at least two versions of thecontent. The at least two versions of the content may be similar (e.g.,or near identical) but may be different based on a difference inwatermarking information. The watermarking information may comprise anytype of information. The watermarking information may comprise, forexample, data added to a frame. The watermarking information may beadded to only one frame of a section (e.g., segment, 2 second segment of48 frames). Though FIG. 3C only shows a single representation of themedia portion 204 of the content, it should be understood that fordifferent user accounts, the second portion may be different (e.g.,based on the watermarking information).

The one or more selection rules may be used to determine which portionsof the content are stored as user-specific content. The one or moreselection rules may be applied (in a deterministic manner) such that thecommon portion is the same for different user accounts. The one or moreselection rules may be applied (in a deterministic manner) such that theuser-specific portions vary only based on the watermarking information.

As shown in FIG. 3C, the one or more selection rules may be used todetermine a first portion 302 a for user-specific storage associatedwith a first user account. The one or more selection rules may be usedto determine a first portion 302 b for user-specific storage associatedwith a second user account. The one or more selection rules may be usedto determine the same common portion (e.g., m0, m1, m2) for both thefirst user account and the second user account.

The system may vary which of the at least two version of content areassociated with (e.g., stored for) a user account. Which of the at leasttwo versions of the content are received may vary on asection-by-section (e.g., segment-by-segment, frame-by-frame) basis. Theversion of the content for a section of content may be selected and/ordetermined randomly. As each section of content varies randomly for eachuser, a plurality of different copies of the content (e.g., which varydifferently based on watermarking information, on a segment-by-segmentbasis) may be stored for a plurality of user accounts.

For a first section (e.g., or segment), a first user account may beassociated with a first version of the content comprising firstwatermarking information (e.g., indicated with an “A” subscript in FIG.3C). For a second section (e.g., or segment), the first user account maybe associated with a second version of the content comprising secondwatermarking information (e.g., indicated with a “B” subscript in FIG.3C). FIG. 3C shows a scenario in which the first user account the storesfirst portion b0 based on content version A, first portion b1 based oncontent version B, and first portion bn based on content version B. Thisscenario also shows that the second user account the stores firstportion b0 based on content version B, first portion b1 based on contentversion B, and first portion bn based on content version A. It should beunderstood that this scenario is not limiting but is only one of manyother scenarios which may result implementing the disclosed approach.Whether the first watermarking information or the second watermarkinginformation is selected for a section may be determined randomly. Byrandomly selecting between the first watermarking information and thesecond watermarking information for each user may result in randomand/or uniquely copies of content (e.g., different combinations of thefirst portions) stored in user-specific storage for different users.

FIG. 3D shows another example of storing of first portions and secondportions 304. The content (e.g., media portion 204) may be stored suchthat the user-specific storage may reference duplicated portions ofcontent in the common storage. The content (e.g., media portion 204),may be subdivided into a first portion 302 and a second portion 304. Thefirst portion 302 may be determined (e.g., using one or more selectionrules). The second portion 304 may be a remaining portion that does notinclude the first portion 302. Both the first portion 302 and the secondportion 304 may be stored in common storage (e.g., as bytes in a commonfile).

The first portion 302 may be stored redundantly in the common storage(e.g., as bytes in the common file). The redundant copies of the firstportion 302 may be duplicated N times. N may be the number of usersstoring the content, a predetermined number, and/or the like. Theredundant copies of the first portion 302 may be stored in the samefile, bit sequence (e.g., sequentially in the bit sequence), and/or thelike. The redundant copies of the first portion 302 may be separated byrandom amounts of random data.

An index file (e.g., Idx₁, Idx₂, Idx_(n)) may be stored in user-specificstorage (e.g., of each user). The index file may be unique to each user(e.g., at least to a portion of users). The index file may reference aspecific redundant copy (e.g., b0₁, b0₂, b0_(n)) of the user-specificportion stored in the common storage. The number of redundant copies ofthe user-specific portion stored in the common storage may be less thana number of a plurality of user accounts associated with storing thecontent. The index file may reference the common portion (m0). Thedashed lines with arrows in FIG. 3D indicate that an index filereferences (e.g., includes a location to access) the first portion 302and the second portion 304. As shown in FIG. 3D, a first user may havean associated first user-specific storage 306 comprising a first indexfile. A second user may have an associated second user-specific storage308 comprising a second index file. A third user may have an associatedthird user-specific storage (e.g., not shown) comprising a third indexfile. The first user, second user, and third user may each be associatedwith different (e.g., unique) copies of the content. The user-specificportion for each of the copies of the content may be different and/orunique. The data stored in the first user-specific storage 306 may bedifferent from the data stored in other user-specific storages (e.g.,based on the index files referring to different first portions).

An index file may comprise an instruction to skip one or more of theredundant copies of the first portion 302 stored in the common storage.The index file may comprise an instruction to skip random bytes in thecommon storage. The index file may comprise an instruction to skipredundant copies of first portion 302, access the copy of the firstportion associated with the user, and/or access the common portionassociated with the user.

An example data file (e.g., video stream data, bit stream data, videodata, audio data) can be stored for a plurality of users. The data filecan comprise a CABAC-coded file. For purposes of illustration, the datafile can comprise 100 bytes, but it should be understood that any filesize can be used. N may be selected as 20 bytes, starting at byte O. Mwould then be selected as the remaining 80 bytes (e.g., 100−20). Thefirst 20 bytes may be copied in to a file in the common storage 42 times(e.g., or any other number). Following these 42 copies, the remaining 80bytes may be stored in the file. The file may comprise 920 bytes.

For user accounts u=0 . . . 41, a byte range may be calculated as [u*20,(u+1)*20)], which is the u-th 20-byte range. This byte range (e.g., asb0_(1-n), b1_(1-n)) or data indicative of this byte range (e.g., ifstored in common storage) may be copied into common storage. Dataindicating the location of a corresponding byte range may be stored inthe user-specific storage for a corresponding user account. Remainingportions of the content not included in the byte range may be stored inthe common portion (e.g., along with copies of the byte range). For useraccount 0, the byte range may comprise [0,20]. In user-specific storageassociated with user account 0, a record may be stored indicating aninstruction to access the [0,20] byte range from common storage. Foruser account 1, the byte range may comprise [20, 40]. In user-specificstorage associated with user account 1, a record may be storedindicating an instruction to access the [20,40] byte range from commonstorage.

The records may be stored in corresponding indexes associated with thefirst user account and/or the second user account. An index may comprisea “skip” instruction for the first u*20 bytes, a “copy fromuser-specific storage” instruction for 20 bytes, a “skip” instructionfor (42−u+1)*20 bytes, a “copy from the common portion” instruction forlast 80 bytes, or a combination thereof. These instructions may be usedto determine (e.g., or reconstitute) the content by combining thecorresponding first portions (e.g., b0, b1, b2) and second portions(e.g., m0, m1, m2, etc.) for a plurality of sections of the content. Itshould be understood that different users may have different index filesthat copy, access, and/or skip different portions of the redundantcopies of the user-specific portion.

It should be appreciated that the one or more of the aspects shown inFIGS. 3A-D may be combined. For example, an aspect shown in FIG. 3B maybe combined with any one of the aspects of FIGS. 3A, 3C, and/or 3D. Anaspect shown in FIG. 3C may be combined with any one of the aspects ofFIGS. 3A, 3B, and/or 3D. An aspect shown in FIG. 3D may be combined withany one of the aspects of FIGS. 3A, 3B, and/or 3C. The watermarkingtechniques associated with FIG. 3C may be used in combination with therandomized additional data techniques associated with FIG. 3B.

FIG. 4 shows an example implementation of a user-specific storageformat. The user-specific storage format may be used to storeuser-specific data as one or more files. The user-specific data may beassociated with a specific content recording, content asset, contentchannel, a user associated with the recording, a combination thereofand/or the like. The user-specific data may comprise a header 402, afirst index 404, a second index 406, user-specific bytes 408 (e.g.,user-specific portion of the content), a combination thereof, and/or thelike.

The header 402 may comprise data (e.g., metadata) indicating the syntaxof one more indices, such as the first index 404 and the second index406. The syntax data indicating the syntax may comprise one or morefield identifiers, field lengths, hash and encryption algorithms, hashesdata (e.g., hashes of the contain-specific portion, hashes of the commonportion), encryption keys, key identifiers, initialization vector (IV),additional authenticated data (AAD), a combination thereof, and/or thelike.

The first index 404 may be associated with and/or comprise data relatedto one or more media portions of the content, such as first portionsstored in user-specific storage and second portions stored in commonstorage. The first index 404 may comprise a plurality of entries (e.g.,or records). An entry may comprise one or more fields, such as a numberof bytes to copy from the user-specific bytes 408, number of bytes tocopy from the common storage (e.g., bytes from a corresponding commonfile in the common storage), a number of times an operation indicate inthe entry should be repeated, a combination thereof, and/or the like.The one or more fields may be used to indicate bytes in a file of thecommon storage to skip, a modification of the blocks in the commonstorage (e.g., application of XOR to mantle blocks), and/or the like.

The second index 406 may be associated with and/or comprise data relatedto one or more header data of the content (e.g., first portion,container-specific portion, the header portion 202 of FIG. 2 ). Thesecond index 406 may comprise a plurality of entries (e.g., or records).An entry may comprise one or more fields, such as a number of bytes tocopy from the reconstructed content (e.g., the bitstream filereconstructed using the user-specific portion and the common portion), anumber of bytes to copy from the header data of the content, acombination thereof, and/or the like.

The user-specific bytes 408 may comprise user-specific portions (e.g.,first portions) copied from the content (e.g., bitstream) by thedeconstruction process illustrated in FIGS. 3A-D. The user-specificbytes 408 may be encrypted. If the user-specific bytes 408 areencrypted, key information for decrypting the user-specific bytes may bestored in the header 402.

FIG. 5 shows an example system 500. The system 500 may be at least apart of the storage device 104 of FIG. 1 (e.g., or be one or more nodes,devices, or services implementing features of the storage device 104).The system may be configured for storage of content items, such ascontent items recorded from one or more of a plurality content streams.The system 500 may determine a content section 502 of a content item.The content section 502 may be determined based on receiving the contentsection 502 as part of a content stream of the plurality of contentsections. The content section 502 may be determined (e.g., or received)by a storage service 504 (e.g., or compression service).

The storage service 504 may be configured to determine, based on thecontent section 502, a plurality of user-specific portions 506. Theplurality of user-specific portions 506 may each be a separate copy of adetermined user-specific portion. The separate copies may be identicalcopies, or may be varied according to the techniques described herein.The storage service 504 may be configured to determine, based on thecontent section 502, a common portion 508. The storage service 504 maysubdivide the content section 502 into the common portion and theplurality of user-specific portions 506. The system 500 may beconfigured store only one copy of the common portion 508 for eachsection of a content item. The system 500 may be configured to storemany copies of the corresponding user-specific portions, for eachsection of the content item.

If a playback request for a section is received, one of the plurality ofuser-specific portions 506 and the common portion 508 may be recombinedto create a playable section of the content item. This approach mayresult in the same common portion being read from a storage subsystemrepeatedly if multiple users are accessing the stored content based ofthe same original source stream, which may be highly inefficient. Oneapproach to solve this problem is to cache all the common portions, butthere are major problems with this approach. Cache memory is finite, andthe amount of stored content is far larger than what is available incache. This approach may also waste memory to cache something that noother user will use before it expires from cache. Disclosed herein aremethods and systems for more efficiently accessing and storing content.

FIG. 6 shows an example system 600. The system 600 may be configured tofacilitate playback of stored (e.g., recorded content), such as contentstored using the system of FIG. 1 and/or FIG. 5 (e.g., using anyprocessing disclosed herein). The system 600 may comprise a user device602. The user device 602 may comprise any user device, such as acomputing device, smart device (e.g., smart glasses, smart watch, smartphone), a mobile device, a tablet, a computing station, a laptop, adigital streaming device, a set-top box, a streaming stick, atelevision, and/or the like. The user device 602 may be associated witha user account. The user device 602 may be associated with the useraccount based on authentication of the user device using credentialsassociated with the user account.

The user device 602 may be configured to access a content storageservice. The content storage service may be facilitated by one moreservices, such as a request service 604, an information storage 606(e.g., or information storage service), a recombination service 608, auser-specific storage 610, a caching service 612, a common storage 614,an analysis service 616, or a combination thereof. The one or moreservices may be implemented by one or more computing nodes, virtualmachines, computing devices, or a combination thereof.

For purposes of illustration, and without limiting the scope of thedisclosure, the following example scenario is provided. Consider thecase where two users are recording ESPN, and a third user is recordingABC. Each recording may be assigned a random identifier, and records thesection (e.g., segment) from the source stream when the recording start.An example table for such a scenario is shown in Table 1.

TABLE 1 Source User Recording ID Source Stream ID Section NumberF69602D2 ESPN 152 4BBF923B ESPN 250 8280DD37 ABC 647

For simplicity, assume that a content recording starts at segment 0, buta different number may be used. In this case, recording 4BBF923B startedrecording ESPN 98 segments after recording R69602D2 started recordingthe same stream.

At step 1, the user device 602 may send a request to the request service604 (e.g., or to the content storage service). The request may comprisea request to access and/or playback a section of a content item. Theuser device 602 may receive (e.g., from the content storage service) anindex (e.g., or manifest) comprising a list of content sections (e.g.,or segments) associated with the stored content item. The index can beaccessed from user-specific storage associated with the user account.The index may be specific to the recording and/or stored content. Thelist of content sections may comprise an identifier, number, contentsection number, uniform resource identifier, and/or the like forspecifically requesting each corresponding section. The request maycomprise a hypertext transfer protocol request. The request may be ofthe form “GET/rec-[recording identifier]/seg-[section identifier].ts”.For example, if the recording identifier is F69602D2, and the first userrequests the section with identifier of “3”, the request may comprise“GET/rec-F69602D2/seg-3.ts”

At step 2, the request service 604 may process the request by sending aquery to the information storage 606. The information storage 606 maycomprise information about a plurality of stored and/or recorded contentitems. The information may comprise source information, source sectioninformation, content item information, stream information, and/or thelike. The system 600 may be configured to track (e.g., number, count)content sections associated with a content source. A content source maycomprise a content channel, such as ESPN or ABC. A content stream fromthe content source may have a plurality of different content items,sequentially sent via the stream. The information may comprise anindication of content sections from a content source that correspond toa stored content item. The request service 604 may determine, based onone or more queries to the information storage 606, that the requestedstored content section is associated with a content source, a sourcecontent section, and/or the like. A recording identifier may beassociated with a beginning source section identifier, an ending sourcesection identifier, a source section range, and/or the like.

The request service 604 may query the information storage 606 todetermine a source stream, a start segment of the source stream, acombination thereof, and/or the like. The request service 604 may send arequest comprising a recording identifier. The information storage 606may return a source identifier (e.g., channel name), a source sectionidentifier, and/or the like. If the query comprises the F69602D2, theresponse to the query may comprise a source identifier of ESPN and asource section identifier of 155. The query may also comprise thesection identifier (e.g., 3). The source section identifier returned bythe query may comprise the source section identifier that corresponds tothe section identifier. If a beginning section identifier is returned,the request service 604 may determine the source section thatcorresponds to the section identifier by incrementing the sourceidentifier by the requested section identifier. For example, the sourcesection identifier 152 may be incremented by 3 to determine a sourcesection identifier of 155.

At step 3, the request service 604 may send the information from theinformation storage 606 to an analysis service 616. The information maycomprise the source identifier, a source section identifiercorresponding to the requested stored content section identifier, and/orthe like.

The analysis service 616 may be configured to store information receivedfrom the request service 604 associated with a plurality of requests.Each time a user device, such as user device 602 requests a contentsection (e.g., or segment), the analysis service 616 may receive amessage indicating the corresponding source identifier and sourcesection identifier. The analysis service 616 may analyze the storedinformation to determine one or more metrics. The one or more metricsmay comprise a count associated with a source content section. The countmay be indicative of a number of user accounts requesting stored contentsections that correspond to the same source content section (e.g., orsource content section identifier). The one or more metrics may comprisea request rate for the content.

The analysis service 616 may be configured to analyze the one or moremetrics based on one or more caching criteria. The one or more cachingcriteria may comprise conditions, thresholds, and/or the like fortriggering caching of content. The analysis service 616 may beconfigured to determine, based on the analysis, caching information. Thecaching information may comprise one or more ranges (e.g., or windows)of content sections. The one or more ranges may comprise a range ofsource content sections, source content section identifiers, and/or thelike. The one or more ranges may comprise a starting source contentsection identifier, an ending source content section identifier, anumber of sections in the range, and/or the like.

At step 4, the analysis service 616 may send the caching information tothe caching service 612. The caching information sent to the cachingservice may comprise the one or more ranges of content sections, thesource identifier, a number of content sections in the range, timinginformation (e.g., number of seconds to retain range in cache storage),and/or the like. A threshold number of requests may be received within athreshold time. If the requests within the threshold time are requestsfor content sections within a threshold range of content sections (e.g.,having a difference between the lowest and highest segment be less thana threshold), then a determination may be made to cache a correspondingrange of content segments (e.g., or sliding window). The correspondingrange may be determined (e.g., calculated) based on one or more of thethreshold range, a predicted range, a default range, and/or the like.The predicted range may be determined based on determining the range ofrequested content segments (e.g., from a lowest to highest). The rangeof requested content segments may be shifted by adding a number to therange (e.g., by adding the number to the lowest to get a new low endand/or to the highest to get a new high end).

If a threshold number of requests (e.g., three, for purposes ofillustration) for content segments are within a threshold range ofcontent segments of each other (e.g., fifteen), a sliding window may bedetermined. If requests are received for segment X, X+10, and X−4, (as asimple non-limiting example) a determination may be made that athreshold number of requests are received within the threshold range(e.g., fifteen) and threshold time (e.g., thirty seconds). A range ofcontent sections and/or sliding window may be determined as the cachinginformation.

The analysis service 616 may determine that a threshold number of usersare requesting content sections that correspond to the source contentrange of [155-185] for ESPN. The caching information sent may comprisean identifier indicative of ESPN, the source content section range of[155-185], an indication to store the range in cache storage for 30seconds, and/or the like. The caching service 612 may receive thecaching information. The caching service 612 may retrieve one or moresecond portions (e.g., one or more common portions) from the commonstorage based on the caching information. The caching service 612 mayretrieve the one or more second portions that correspond to the contentsections in the source content range.

At step 5, the request service 604 may be configured to forward therequest from the user device 602 to the recombination service 608. Therequest may be sent with the information from the information storage606. The information from the information storage 606 may be sent asmetadata associated with the request. The information may be added to(e.g., stored in) one or more header fields of the request. If therequest is an HTTP request, the one or more header fields may compriseHTTP header fields. The one or more header fields may comprise a sourcefield. The source field may store a source identifier (e.g., identifierindicating a content channel). The one or more header fields maycomprise a source segment field. The source segment field may comprise asegment identifier indicating the segment that is requested. Theinformation may comprise the source identifier, the source contentsection identifier, and/or the like. The request may comprise““GET/rec-F69602D2/seg-3.ts” and include a source header “Source: ESPN”and a source section header “SourceSeg: 155”.

At step 6, the recombination service 608 may access a first portion(e.g., a user-specific portion) of a stored content section from theuser-specific storage 610. The first portion may be accessed and/ordetermined based on the request. The first portion may be accessedand/or determined based on the recording identifier and the sectionidentifier. The user-specific storage 610 may be searchable based onrecording identifier and second identifier. The first portion maycorrespond to a portion of the original source content section. Thefirst portion may be a copy of a portion of an original source contentsection received from the content source. The first portion may compriseadditional information and/or comprise a version of the portion of theoriginal source content section. The copy of the first portion may bestored (e.g., temporarily) in storage associated with the recombinationservice 608.

At step 7, the recombination service 608 may send a request to thecaching service 612 for a second portion (e.g., a common portion). Therequest may comprise the source identifier and/or the source sectionidentifier. The recombination service 608 may replace the recordingidentifier with the corresponding source identifier in generating therequest. The recombination service 608 may replace the sectionidentifier with the corresponding source section identifier ingenerating the request. The request may comprise an HTTP request with auniform resource identifier comprising the source identifier and/or thesource section identifier. The request may be of the form“GET/stream-[source identifier]/seg-[source section identifier].ts”. Anexample request may comprise “GET/stream-ESPN/seg-155.ts”. In somescenarios, other HTTP commands may be used instead of GET, such as POST.

The caching service 612 may receive the request from the recombinationservice 608. The caching service 612 may determine if a second portionassociated with the requested content section is stored in cachestorage. If the second portion (e.g., or copy of the second portion) isstored in the cache storage, the caching service 612 may send the secondportion to the recombination service 608. If the second portion is notstored in the cache storage, the caching service 612 determine toretrieve the second portion from the common storage 614. If the secondportion matches caching information received from the analysis service616, the second portion (e.g., or a copy of the second portion) may bestored in the cache storage according to any criteria, such as timinginformation, in the caching information.

At step 8, the caching service 612 may send a request to the commonstorage 614 for the second portion. The request sent to the commonstorage 614 may comprise the request received by the caching service612. The request may comprise the source identifier and/or the sourcecontent section identifier. An example request may comprise“GET/stream-ESPN/seg-155.ts”. In some scenarios, other HTTP commands maybe used instead of GET, such as POST. The common storage 614 maydetermine the second portion associated with the requested contentsection. The source identifier, and/or source content section identifiermay be associated with the second portion (e.g., and be used to accessfinding/accessing the second portion) in the common storage 614.

The second portion determined from the cache storage or the commonstorage 614 may be sent to the recombination service 608. Therecombination service 608 may be configured to determine a combinationof the first portion from the user-specific storage 610 and the secondportion from the cache storage or the common storage 614. Determiningthe combination of the first portion and the second portion may compriseappending the second portion to first portion.

FIG. 7 shows a diagram of example ranges for caching content sections.As shown, the range of content sections indicated in the cachinginformation may be modified over time. One or more ranges of contentsections indicated in the caching information may be implemented as asliding window, rolling window, and/or the like. The one or more rangesmay be adjusted over time to account for anticipated and/or predictedrequests for stored content sections. In some scenarios, multipledifferent ranges of content sections may be implemented for caching onthe same source stream. For example, different groups of user accountsmay be requesting different sections of the same content item atdifferent times.

As a non-limiting illustration, consider the scenario where a largenumber of user accounts request recording of a sporting event as ascheduled recording (e.g., all starting at the same source streamsection number). A few minutes after the recording starts, 1000 useraccounts may start may request access to the new started recordings. Theanalysis service 616 may send, to the caching service 612, the followingtuple: ESPN, [2000-2015], 30. Note that the use of closed bracketsindicates that the beginning and ending numbers indicated are includedin the range. All of the 1000 user accounts are not likely to requestthe same content section at the same time, but the user accounts may beaccessing a content section in a range (e.g., or window). The range(e.g., or window) may be updated as user accounts access the requestedcontent sections. As a non-limiting illustration, an initial range maycomprise content sections [2000-2015]. After 30 seconds, the contentsection range may be updated to a new range of content sections[2015-2030]. An example pattern is shown in Table 2.

TABLE 2 Time Section Range Number of Users 0 A: 2000-2015 1000 30 A:2015-2030 1000 60 A: 2030-2045 1000 90 A: 2045-2060 1000 B: 1000-1015350

After 90 seconds of playback, another group of 350 user accounts maystart requesting content recordings based off the same source stream butfrom an earlier point in time. The analysis service 616 may determine anadditional range of content sections based on the group of 350 users.The caching service 612 may be sent instructions to begin storing twodifferent ranges (e.g., or 2 rolling windows) of content sections forrecordings associated with the same source stream. The first range,range A, may be the content section range [2045-2060] that is associatedwith the initial 1000 user accounts. The second range, range B may bethe content section range [1000-1015] that is associated with the 350user accounts. The analysis service 616 may adjust one or more of thesize of the range or the timing information (e.g., TTL, time to keeprange active) sent to the caching service 612. The adjustments may bebased on the number of user accounts accessing a specific source stream(e.g., or accessing stored content associated with the same content itemand/or source stream), the location within the range of the useraccounts, a combination thereof, and/or the like.

As a non-limiting illustration, consider range B in Table 2 that has 350user accounts associated with the range. If the number of user accountsdrops below a threshold (e.g., 10 users), the range may be eliminated.Elimination of the range may result in the remaining 10 active playbackscausing the second portions to be accessed from the common storage 614instead of the cache storage.

As a non-limiting illustration, another use case may occur if a largenumber of user accounts request content sections at a location betweenrange A and range B. The analysis service 616 may generate a new rangein response to the increase of requests. The new range may comprise athird range. The new range may comprise expansion of one of the otherranges (e.g., range A or range B) if the potential new range is within athreshold number of sections of a pre-existing range (e.g., or if theranges overlap). If a threshold number of user accounts requestedcontent sections in the range [1980-1995], the analysis service 616 maybe configured to determine of a third range. However, if the newlyrequested content sections were in the range [2035-2050], the analysisservice 616 may be configured to cause the expansion of range A to be[2035-2060]. The timing information may also be adjusted, such asincreasing the TTL to account for the increased range size.

As a non-limiting illustration, consider the case where a user accountrequests access to the same sporting event recording, except it is 3 amin the morning, resulting in being the only user account watching thesporting event. In this scenario, the analysis service 616 does not sendany caching information to the caching service 612. Since there is onlyone user account accessing a recording from the source stream, it may beinefficient to cache second portions since content sections are likelyto only be requested once.

FIG. 8 is a flow diagram showing an example method 800. The method 800can comprise a computer implemented method. The method 800 can beimplemented by one or more devices (e.g., computing devices, servers)and/or services disclosed herein, such as the devices, storage, and/orservices of FIG. 1 , FIG. 5 , and FIG. 6 .

At step 802, a first portion of a content item and a second portion ofthe content item may be determined (e.g., determined for storing,determined from storage, stored, accessed). The first portion may bedetermined in each of a plurality of user-specific storages associatedwith corresponding user accounts of a plurality of user accounts. Thesecond portion of the content item may be determined in a common storageassociated with the plurality of user accounts.

The first portion may comprise a first portion of a content section(e.g., content segment). The second portion may comprise a secondportion of the content section. The first portion and the second portionmay be generated (e.g., determined) as part of a network based contentrecording service. The plurality of user accounts may be accountsassociated with the content recording service. The content item maycomprise a content stream, content file, and/or the like. The contentitem may comprise a plurality of sections (e.g., segments, such as a 2second segment). To store the content item for later access, eachsection may be subdivided into at least one first portion and at leastone second portion, as described further herein. A first portion maycomprise a first portion of a sequence of bits and the second portionmay comprise a second portion of the sequence of bits. The secondportion of the sequence of bits may comprise bits directly after (e.g.,the first bit in the second portion may be the next bit in the sequenceof bits after the last bit in the first portion) the first portion ofthe sequence of bits. Additional data (e.g., bits) may be combined withthe first portion and/or the second portion. For different useraccounts, different copies of the first portion may be stored incorresponding user-specific storage associated with respective useraccounts of the plurality of user accounts. For each section, a singlecopy of the second portion may be stored in the common storage foraccess by each of the plurality of user accounts. The first portion andthe second portion may be subportions of a media portion of the contentitem (e.g., media portion 204 shown in FIG. 2 ).

At step 804, it may be determined that one or more caching criteria issatisfied. The determination may be based on a plurality of requestsassociated with receiving (e.g., or accessing) the stored content item.The plurality of requests may be requests for a section of the contentbefore a section of the content item comprising the first portion andthe second portion. The plurality of requests may be requests for thesection of the content item comprising the first portion and the secondportion. The one or more caching criteria may comprise a thresholdnumber of the plurality of user accounts being associated withrequesting the stored content item. The one or more caching criteria maycomprise a range indicating a subset of one or more sections of thecontent item associated with active playback of the content item for atleast a portion of the plurality of user accounts. Each of the one ormore sections may comprise a corresponding first portion and secondportion. The range may be updated over time as one or more of theplurality of user accounts progress in playback of the content item.

At step 806, storage of the second portion in a cache storage differentfrom the common storage may be caused. The storage of the second portionin the cache storage different from the common storage may be causedbased on the one or more caching criteria being satisfied. Causingstorage of the second portion in the cache storage may comprise causinga copy of the second portion (e.g., or moving the second portion) to bestored in the cache storage until the one or more caching criteria areno longer satisfied. The cache storage may be temporary storage.

The second portion may be caused to be stored in the cache storage basedon the second portion being associated with the subset. The secondportion may comprise a common portion that matches the range. The commonportion may match the range based on the common portion being associatedwith a content section of source content (e.g., the source content fromwhich the different copies of the stored content item originated). Thesecond portion may be associated with (e.g., in the common storage) asource section identifier. The source section identifier can identify asource content section from which the second portion originated.

At step 808, a first portion from one of the plurality of user-specificstorages and the second portion from the cache storage may be caused tobe sent (e.g., separately or in combination). A combination of the firstportion and the second portion may be caused to be sent. The combinationmay be determined by appending the second portion to the first portionfrom the one of the plurality of user-specific storages. The combinationmay be determined by appending (e.g., or prepending) the second portionto the first portion. The combination of the first portion and thesecond may be determined using one or more combination rules. The one ormore combination rules may be based on the selection rules used todetermine the second portion. The first portion and the second portion(e.g., the combination) may be further combined with header data to forma content section, packet, and/or the like.

The first portion and/or the second portion (e.g., the combination) maybe sent based on (e.g., in response to) an additional request associatedwith accessing the stored content item. The additional request maycomprise a request from a user account (e.g., associated with the one ofthe plurality of user-specific storages) for the section of the contentitem. A computing device may be configured to process the request forthe section of the content item by determining the first portionassociated with the user account and second portion. The computingdevice may send a request for the second portion located in the commonstorage. A storage device associated with the common storage and/oranother portion of the computing device may receive the request for thesecond portion located in the common storage. The request may beprocessed (e.g., by the storage device, computing device) by determiningthe second portion located in the cache storage (e.g., instead ofdetermining the second portion located in common storage).

The combination of the one of a first portion from one of the pluralityof user-specific storages and the second portion from the cache storagemay be sent in response to the request from the user account. Thecombination may be sent via a network, such as a content access network,to a user device associated with the user account. The section of thecontent may be output via a display of the user device.

FIG. 9 is a flow diagram showing an example method. The method 900 cancomprise a computer implemented method. The method 900 can beimplemented by one or more devices (e.g., computing devices, servers)and/or services disclosed herein, such as the devices, storage, and/orservices of FIG. 1 , FIG. 5 , and FIG. 6 .

At step 902, a first portion of a content item and a second portion ofthe content item may be determined (e.g., or determined for storing,stored, accessed). The first portion may be determined in each of aplurality of user-specific storages associated with corresponding useraccounts of a plurality of user accounts. The second portion of thecontent item may be determined (e.g., or determined for storing, stored,accessed) in a common storage associated with the plurality of useraccounts.

The first portion may comprise a first portion of a content section(e.g., content segment). The second portion may comprise a secondportion of the content section. The first portion and the second portionmay be generated (e.g., determined) as part of a network based contentrecording service. The plurality of user accounts may be accountsassociated with the content recording service. The content item maycomprise a content stream, content file, and/or the like. The contentitem may comprise a plurality of sections (e.g., segments, such as a 2second segment). To store the content item for later access, eachsection may be subdivided into at least one first portion and at leastone second portion, as described further herein. A first portion maycomprise a first portion of a sequence of bits and the second portionmay comprise a second portion of the sequence of bits. The secondportion of the sequence of bits may comprise bits directly after (e.g.,the first bit in the second portion may be the next bit in the sequenceof bits after the last bit in the first portion) the first portion ofthe sequence of bits. Additional data (e.g., bits) may be combined withthe first portion and/or the second portion. For different useraccounts, different copies of the first portion may be stored incorresponding user-specific storage associated with respective useraccounts of the plurality of user accounts. For each section, a singlecopy of the second portion may be stored in the common storage foraccess by each of the plurality of user accounts. The first portion andthe second portion may be subportions of a media portion of the contentitem (e.g., media portion 204 shown in FIG. 2 ).

At step 904, it may be determined that one or more caching criteria isnot satisfied. It may be determined that the one or more cachingcriteria is not satisfied for at least a portion of the stored contentitem. The one or more caching criteria may comprise a threshold numberof the plurality of user accounts being associated with requesting thesecond portion of the stored content item.

The one or more caching criteria may comprise a range indicating asubset of one or more sections of the content item associated withactive playback of the content item for at least a portion of theplurality of user accounts. Each of the one or more sections maycomprise a corresponding first portion and second portion. The range maybe updated over time to include subsequent sections of the content itemas one or more of the plurality of user accounts progress in playback ofthe content item. The range may be associated with timing informationindicative of a length of time to use the range for caching decisions.

At step 906, the second portion may be caused to be removed from a cachestorage different from the common storage. The cache storage may betemporary storage. The second portion may be caused to be removed fromthe cache storage different from the common storage based on the one ormore caching criteria not being satisfied. Causing the second portion tobe removed from the cache storage may comprise deleting a copy of thesecond portion, moving a copy of the second portion from the cachestorage to the common storage, a combination thereof, and/or the like.

At step 908, a first portion from one of the plurality of user-specificstorages and the second portion from the common storage may be caused tobe sent (e.g., separately or in combination). The second portion beappended to the first portion. A combination of the first portion andthe second portion may be determined by appending (e.g., or prepending)the second portion to the first portion. The combination of the firstportion and the second portion may be determined using one or morecombination rules. The one or more combination rules may be based on theselection rules used to determine the second portion. The first portionand/or the second portion (e.g., or the combination) may be furthercombined with header data to form a content section, packet, and/or thelike.

The first portion and the second portion (e.g., combination) may be sentbased on (e.g., in response to) a request associated with accessing thestored content item. The request may comprise a request from a useraccount (e.g., associated with the one of the plurality of user-specificstorages) for the section of the content item. A computing device may beconfigured to process the request for the section of the content item bydetermining the first portion associated with the user account andsecond portion. The computing device may send a request for the secondportion located in the common storage. A storage device associated withthe common storage and/or another portion of the computing device mayreceive the request for the second portion located in the commonstorage. The request may be processed (e.g., by the storage device,computing device) by determining the second portion located in thecommon storage (e.g., instead of determining the second portion locatedin common storage). The request may be processed by verifying that thesecond portion is not located in the cache storage.

The first portion from one of the plurality of user-specific storagesand the second portion from the common storage (e.g., or combination)may be sent in response to the request from the user account. The firstportion and the second portion (e.g., or the combination) may be sentvia a network, such as a content access network, to a user deviceassociated with the user account. The section of the content may beoutput via a display of the user device.

FIG. 10 is a flow diagram showing an example method 1000. The method1000 can comprise a computer implemented method. The method can beimplemented by one or more devices (e.g., computing devices, servers)and/or services disclosed herein, such as the devices, storage, and/orservices of FIG. 1 , FIG. 5 , and FIG. 6 .

At step 1002, a plurality of requests associated with a stored contentitem may be received. A first portion of the content item may be storedin (e.g., or determined for) each of a plurality of user-specificstorages associated with corresponding user accounts of a plurality ofuser accounts. A second portion of the content item may be stored in(e.g., or determined for) common storage.

The first portion may comprise a first portion of a content section(e.g., content segment). The second portion may comprise a secondportion of the content section. The first portion and the second portionmay be generated (e.g., determined) as part of a network based contentrecording service. The plurality of user accounts may be accountsassociated with the content recording service. The content item maycomprise a content stream, content file, and/or the like. The contentitem may comprise a plurality of sections (e.g., segments, such as a 2second segment). To store the content item for later access, eachsection may be subdivided into at least one first portion and at leastone second portion, as described further herein. A first portion maycomprise a first portion of a sequence of bits and the second portionmay comprise a second portion of the sequence of bits. The secondportion of the sequence of bits may comprise bits directly after (e.g.,the first bit in the second portion may be the next bit in the sequenceof bits after the last bit in the first portion) the first portion ofthe sequence of bits. Additional data (e.g., bits) may be combined withthe first portion and/or the second portion. For different useraccounts, different copies of the first portion may be stored incorresponding user-specific storage associated with respective useraccounts of the plurality of user accounts. For each section, a singlecopy of the second portion may be stored in the common storage foraccess by each of the plurality of user accounts. The first portion andthe second portion may be subportions of a media portion of the contentitem (e.g., media portion 204 shown in FIG. 2 ).

At step 1004, a first range indicating a first subset of the contentitem may be determined. The first subset may comprise one or morecontent sections (e.g., or segments, packets). The first range may bedetermined based on (e.g., in response to) receiving the plurality ofrequests. The first subset of the content item may be predicted to berequested within a time window based on prior requests. The first rangemay be associated with timing information indicative of a length of timeto use the first range for caching decisions.

The first range may be determined based on one or more caching criteria.The one or more caching criteria may comprise a threshold number of theplurality of user accounts being associated with requesting the storedcontent item. The one or more caching criteria may comprise a thresholdnumber of the plurality of user accounts being associated withrequesting a second subset of content items within a threshold time. Thefirst subset of content items may be sequentially after the secondsubset. The first subset may be predicted to be requested based on ahistory of plurality of user accounts requesting the first subset.

At step 1006, the second portion may be caused to be stored in a cachestorage different from the common storage. The second portion may becaused to be stored in the cache storage based on the second portionbeing associated with the first subset. The second portion may comprisea common portion that matches the first range. The common portion maymatch the first range based on the common portion being associated witha content section of source content (e.g., the source content from whichthe different copies of the stored content item originated). The secondportion may be associated with (e.g., in the common storage) with asource section identifier. The source section identifier can identify asource content section from which the second portion originated.

At step 1008, a first portion from one of the plurality of user-specificstorages and the second portion from the cache storage may be caused tobe sent (e.g., separately or in combination). The first portion and thesecond portion (e.g., a combination thereof) may be sent based on anadditional request associated with accessing the content item. Theadditional request may be for a section of the content item associatedwith the first portion and the second portion. A combination of thefirst portion and the second portion may be determined by appending(e.g., or prepending) the second portion to the first portion from theone of the plurality of user-specific storages. The combination of thefirst portion and the second may be determined using one or morecombination rules. The one or more combination rules may be based on theselection rules used to determine the second portion. The first portionand/or second portion (e.g., or the combination) may be further combinedwith header data to form a content section, packet, and/or the like.

The first range may be updated. The first range may be updated based ona change in a number of user accounts requesting the stored contentitem. One or more additional second portions may be caused to be removedor added to the cache storage. The one or more additional secondportions may be caused to be removed or added to the cache storage basedon updating the first range.

A second range indicating a second subset of the content item differentfrom the first subset may be determined. The second range may bedetermined based on receiving the plurality of requests. The secondsubset may be associated with additional first portions of the contentitem stored in the plurality of user-specific storages. The secondsubset may be associated with an additional second portion stored in thecommon storage. The additional second portion may be caused to be storedin the cache storage.

The first range and the second range may be merged into a combinedrange. The first range and the second range may be merged into acombined range based on the first range being within a threshold windowapart from the second range. The threshold window may comprise a timewindow (e.g., the first range may be within a threshold number ofseconds before or after the second ranger), a numbering window (e.g.,the segment numbers for the first range may be with a thresholddifference from the segment numbers of the second range), and/or thelike.

FIG. 11 shows a computing device that may be used in various aspects,such as any of the devices shown in FIG. 1 . With regard to the examplearchitecture of FIG. 1 , the content device 102, the user device 106,the storage device 104 may each be implemented in an instance of acomputing device 1100 of FIG. 11 . Any of the user device 602, requestservice 604, information storage 606, recombination service 608,user-specific storage 610, caching service 612, common storage 614,analysis service 616, or a combination thereof of FIG. 6 may beimplemented as one or more instances of the computing device 1100 ofFIG. 11 . The computer device shown in FIG. 11 shows a conventionalserver computer, workstation, desktop computer, laptop, tablet, networkappliance, PDA, e-reader, digital cellular phone, or other computingnode, and may be utilized to execute any aspects of the computersdescribed herein, such as to implement any of the systems and/or themethods described in relation to FIGS. 1-10 .

The computing device 1100 may include a baseboard, or “motherboard,”which is a printed circuit board to which a multitude of components ordevices may be connected by way of a system bus or other electricalcommunication paths. One or more central processing units (CPUs) 1104may operate in conjunction with a chipset 1106. The CPU(s) 1104 may bestandard programmable processors that perform arithmetic and logicaloperations necessary for the operation of the computing device 1100.

The CPU(s) 1104 may perform the necessary operations by transitioningfrom one discrete physical state to the next through the manipulation ofswitching elements that differentiate between and change these states.Switching elements may generally include electronic circuits thatmaintain one of two binary states, such as flip-flops, and electroniccircuits that provide an output state based on the logical combinationof the states of one or more other switching elements, such as logicgates. These basic switching elements may be combined to create morecomplex logic circuits including registers, adders-subtractors,arithmetic logic units, floating-point units, and the like.

The CPU(s) 1104 may be augmented with or replaced by other processingunits, such as GPU(s) 1105. The GPU(s) 1105 may comprise processingunits specialized for but not necessarily limited to highly parallelcomputations, such as graphics and other visualization-relatedprocessing.

A chipset 1106 may provide an interface between the CPU(s) 1104 and theremainder of the components and devices on the baseboard. The chipset1106 may provide an interface to a random access memory (RAM) 1108 usedas the main memory in the computing device 1100. The chipset 1106 mayfurther provide an interface to a computer-readable storage medium, suchas a read-only memory (ROM) 1120 or non-volatile RAM (NVRAM) (notshown), for storing basic routines that may help to start up thecomputing device 1100 and to transfer information between the variouscomponents and devices. ROM 1120 or NVRAM may also store other softwarecomponents necessary for the operation of the computing device 1100 inaccordance with the aspects described herein.

The computing device 1100 may operate in a networked environment usinglogical connections to remote computing nodes and computer systemsthrough local area network (LAN) 1116. The chipset 1106 may includefunctionality for providing network connectivity through a networkinterface controller (NIC) 1122, such as a gigabit Ethernet adapter. AMC 1122 may be capable of connecting the computing device 1100 to othercomputing nodes over a network 1116. It should be appreciated thatmultiple NICs 1122 may be present in the computing device 1100,connecting the computing device to other types of networks and remotecomputer systems.

The computing device 1100 may be connected to a mass storage device 1128that provides non-volatile storage for the computer. The mass storagedevice 1128 may store system programs, application programs, otherprogram modules, and data, which have been described in greater detailherein. The mass storage device 1128 may be connected to the computingdevice 1100 through a storage controller 1124 connected to the chipset1106. The mass storage device 1128 may consist of one or more physicalstorage units. A storage controller 1124 may interface with the physicalstorage units through a serial attached SCSI (SAS) interface, a serialadvanced technology attachment (SATA) interface, a fiber channel (FC)interface, or other type of interface for physically connecting andtransferring data between computers and physical storage units.

The computing device 1100 may store data on a mass storage device 1128by transforming the physical state of the physical storage units toreflect the information being stored. The specific transformation of aphysical state may depend on various factors and on differentimplementations of this description. Examples of such factors mayinclude, but are not limited to, the technology used to implement thephysical storage units and whether the mass storage device 1128 ischaracterized as primary or secondary storage and the like.

For example, the computing device 1100 may store information to the massstorage device 1128 by issuing instructions through a storage controller1124 to alter the magnetic characteristics of a particular locationwithin a magnetic disk drive unit, the reflective or refractivecharacteristics of a particular location in an optical storage unit, orthe electrical characteristics of a particular capacitor, transistor, orother discrete component in a solid-state storage unit. Othertransformations of physical media are possible without departing fromthe scope and spirit of the present description, with the foregoingexamples provided only to facilitate this description. The computingdevice 1100 may further read information from the mass storage device1128 by detecting the physical states or characteristics of one or moreparticular locations within the physical storage units.

In addition to the mass storage device 1128 described above, thecomputing device 1100 may have access to other computer-readable storagemedia to store and retrieve information, such as program modules, datastructures, or other data. It should be appreciated by those skilled inthe art that computer-readable storage media may be any available mediathat provides for the storage of non-transitory data and that may beaccessed by the computing device 1100.

By way of example and not limitation, computer-readable storage mediamay include volatile and non-volatile, transitory computer-readablestorage media and non-transitory computer-readable storage media, andremovable and non-removable media implemented in any method ortechnology. Computer-readable storage media includes, but is not limitedto, RAM, ROM, erasable programmable ROM (“EPROM”), electrically erasableprogrammable ROM (“EEPROM”), flash memory or other solid-state memorytechnology, compact disc ROM (“CD-ROM”), digital versatile disk (“DVD”),high definition DVD (“HD-DVD”), BLU-RAY, or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage, other magneticstorage devices, or any other medium that may be used to store thedesired information in a non-transitory fashion.

A mass storage device, such as the mass storage device 1128 depicted inFIG. 11 , may store an operating system utilized to control theoperation of the computing device 1100. The operating system maycomprise a version of the LINUX operating system. The operating systemmay comprise a version of the WINDOWS SERVER operating system from theMICROSOFT Corporation. According to further aspects, the operatingsystem may comprise a version of the UNIX operating system. Variousmobile phone operating systems, such as IOS and ANDROID, may also beutilized. It should be appreciated that other operating systems may alsobe utilized. The mass storage device 1128 may store other system orapplication programs and data utilized by the computing device 1100.

The mass storage device 1128 or other computer-readable storage mediamay also be encoded with computer-executable instructions, which, whenloaded into the computing device 1100, transforms the computing devicefrom a general-purpose computing system into a special-purpose computercapable of implementing the aspects described herein. Thesecomputer-executable instructions transform the computing device 1100 byspecifying how the CPU(s) 1104 transition between states, as describedabove. The computing device 1100 may have access to computer-readablestorage media storing computer-executable instructions, which, whenexecuted by the computing device 1100, may perform the methods describedherein.

A computing device, such as the computing device 1100 depicted in FIG.11 , may also include an input/output controller 1132 for receiving andprocessing input from a number of input devices, such as a keyboard, amouse, a touchpad, a touch screen, an electronic stylus, or other typeof input device. Similarly, an input/output controller 1132 may provideoutput to a display, such as a computer monitor, a flat-panel display, adigital projector, a printer, a plotter, or other type of output device.It will be appreciated that the computing device 1100 may not includeall of the components shown in FIG. 11 , may include other componentsthat are not explicitly shown in FIG. 11 , or may utilize anarchitecture completely different than that shown in FIG. 11 .

As described herein, a computing device may be a physical computingdevice, such as the computing device 1100 of FIG. 11 . A computing nodemay also include a virtual machine host process and one or more virtualmachine instances. Computer-executable instructions may be executed bythe physical hardware of a computing device indirectly throughinterpretation and/or execution of instructions stored and executed inthe context of a virtual machine.

It is to be understood that the methods and systems are not limited tospecific methods, specific components, or to particular implementations.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other components, integers or steps.“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Components are described that may be used to perform the describedmethods and systems. When combinations, subsets, interactions, groups,etc., of these components are described, it is understood that whilespecific references to each of the various individual and collectivecombinations and permutations of these may not be explicitly described,each is specifically contemplated and described herein, for all methodsand systems. This applies to all aspects of this application including,but not limited to, operations in described methods. Thus, if there area variety of additional operations that may be performed it isunderstood that each of these additional operations may be performedwith any specific embodiment or combination of embodiments of thedescribed methods.

As will be appreciated by one skilled in the art, the methods andsystems may take the form of an entirely hardware embodiment, anentirely software embodiment, or an embodiment combining software andhardware aspects. Furthermore, the methods and systems may take the formof a computer program product on a computer-readable storage mediumhaving computer-readable program instructions (e.g., computer software)embodied in the storage medium. More particularly, the present methodsand systems may take the form of web-implemented computer software. Anysuitable computer-readable storage medium may be utilized including harddisks, CD-ROMs, optical storage devices, or magnetic storage devices.

Embodiments of the methods and systems are described herein withreference to block diagrams and flowchart illustrations of methods,systems, apparatuses and computer program products. It will beunderstood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, may be implemented by computerprogram instructions. These computer program instructions may be loadedon a general-purpose computer, special-purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain methods or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto may be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically described, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe described example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the described example embodiments.

It will also be appreciated that various items are illustrated as beingstored in memory or on storage while being used, and that these items orportions thereof may be transferred between memory and other storagedevices for purposes of memory management and data integrity.Alternatively, in other embodiments, some or all of the software modulesand/or systems may execute in memory on another device and communicatewith the illustrated computing systems via inter-computer communication.Furthermore, in some embodiments, some or all of the systems and/ormodules may be implemented or provided in other ways, such as at leastpartially in firmware and/or hardware, including, but not limited to,one or more application-specific integrated circuits (“ASICs”), standardintegrated circuits, controllers (e.g., by executing appropriateinstructions, and including microcontrollers and/or embeddedcontrollers), field-programmable gate arrays (“FPGAs”), complexprogrammable logic devices (“CPLDs”), etc. Some or all of the modules,systems, and data structures may also be stored (e.g., as softwareinstructions or structured data) on a computer-readable medium, such asa hard disk, a memory, a network, or a portable media article to be readby an appropriate device or via an appropriate connection. The systems,modules, and data structures may also be transmitted as generated datasignals (e.g., as part of a carrier wave or other analog or digitalpropagated signal) on a variety of computer-readable transmission media,including wireless-based and wired/cable-based media, and may take avariety of forms (e.g., as part of a single or multiplexed analogsignal, or as multiple discrete digital packets or frames). Suchcomputer program products may also take other forms in otherembodiments. Accordingly, the present invention may be practiced withother computer system configurations.

While the methods and systems have been described in connection withpreferred embodiments and specific examples, it is not intended that thescope be limited to the particular embodiments set forth, as theembodiments herein are intended in all respects to be illustrativerather than restrictive.

It will be apparent to those skilled in the art that variousmodifications and variations may be made without departing from thescope or spirit of the present disclosure. Other embodiments will beapparent to those skilled in the art from consideration of thespecification and practices described herein. It is intended that thespecification and example figures be considered as exemplary only, witha true scope and spirit being indicated by the following claims.

What is claimed:
 1. A method comprising: determining a first portion ofa content item in each of a plurality of user-specific storagesassociated with corresponding user accounts of a plurality of useraccounts and determining a second portion of the content item in acommon storage associated with the plurality of user accounts;determining, based on a plurality of requests associated with receivingthe stored content item, that one or more caching criteria is satisfied;determining, based on the determining that one or more caching criteriais satisfied, to store the second portion in cache storage differentfrom the common storage; causing, based on the determining to store thesecond portion in the cache storage, storage of the second portion inthe cache storage different from the common storage; and causing sendingof a first portion from one of the plurality of user-specific storagesand the second portion from the cache storage.
 2. The method of claim 1,wherein at least a portion of the content item is being recorded whilethe second portion is caused to be stored in the cache storage.
 3. Themethod of claim 1, wherein the at least a portion of the stored contentitem is requested by at least a portion of users of the plurality ofuser accounts before the content item is finished being recorded.
 4. Themethod of claim 1, further comprising counting a number of the pluralityof user accounts currently accessing at least a portion of the contentitem and updating, based on a change in the number, the cachingcriteria.
 5. The method of claim 1, wherein the one or more cachingcriteria comprises a range of a plurality of segments of the contentitem predicted to be accessed by at least a portion of the plurality ofuser accounts engaged in active playback of the content item.
 6. Themethod of claim 1, wherein the caching criteria is updated over time asone or more of the plurality of user accounts progress in playback ofthe content item.
 7. The method of claim 1, wherein the first portioncomprises a first portion of a content section and the second portioncomprises a second portion of the content section, and furthercomprising appending the second portion to the first portion from theone of the plurality of user-specific storages.
 8. A method comprising:determining a first portion of a content item in each of a plurality ofuser-specific storages associated with corresponding user accounts of aplurality of user accounts and determining a second portion of thecontent item in a common storage associated with the plurality of useraccounts; determining that one or more caching criteria is not satisfiedfor at least a portion of the stored content item; determining, based onthe determining that one or more caching criteria is not satisfied, toremove the second portion from cache storage different from the commonstorage; causing, based on the determining to remove the second portionfrom the cache storage, the second portion to be removed from the cachestorage different from the common storage; and causing sending of afirst portion from one of the plurality of user-specific storages andthe second portion from the common storage.
 9. The method of claim 8,wherein at least a portion of the content item is being recorded whilethe second portion is caused to be stored in the cache storage.
 10. Themethod of claim 8, wherein the at least a portion of the stored contentitem is requested by at least a portion of users of the plurality ofuser accounts before the content item is finished being recorded. 11.The method of claim 8, further comprising counting a number of theplurality of user accounts currently accessing at least a portion of thecontent item and updating, based on a change in the number, the cachingcriteria.
 12. The method of claim 8, wherein the one or more cachingcriteria comprises a range of a plurality of segments of the contentitem predicted to be accessed by at least a portion of the plurality ofuser accounts engaged in active playback of the content item.
 13. Themethod of claim 12, wherein the range is updated over time to includesubsequent segments of the content item as one or more of the pluralityof user accounts progress in playback of the content item.
 14. Themethod of claim 12, wherein the range is associated with timinginformation indicative of a length of time to use the range for cachingdecisions.
 15. A device comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the device to: determine a first portion of a content item in eachof a plurality of user-specific storages associated with correspondinguser accounts of a plurality of user accounts and determine a secondportion of the content item in a common storage associated with theplurality of user accounts; determine, based on a plurality of requestsassociated with receiving the stored content item, that one or morecaching criteria is satisfied; determine, based on the determining thatone or more caching criteria is satisfied, to store the second portionin cache storage different from the common storage; cause, based on thedetermining to store the second portion in the cache storage, storage ofthe second portion in the cache storage different from the commonstorage; and cause sending of a first portion from one of the pluralityof user-specific storages and the second portion from the cache storage.16. The device of claim 15, wherein at least a portion of the contentitem is being recorded while the second portion is caused to be storedin the cache storage.
 17. The device of claim 15, wherein the at least aportion of the stored content item is requested by at least a portion ofusers of the plurality of user accounts before the content item isfinished being recorded.
 18. The device of claim 15, wherein theinstructions, when executed by the one or more processors, further causethe device to count a number of the plurality of user accounts currentlyaccessing at least a portion of the content item and update, based on achange in the number, the caching criteria.
 19. The device of claim 15,wherein the one or more caching criteria comprises a range of aplurality of segments of the content item predicted to be accessed by atleast a portion of the plurality of user accounts engaged in activeplayback of the content item.
 20. The device of claim 15, wherein thecaching criteria is updated over time as one or more of the plurality ofuser accounts progress in playback of the content item.
 21. The deviceof claim 15, wherein the first portion comprises a first portion of acontent section and the second portion comprises a second portion of thecontent section, and further comprising appending the second portion tothe first portion from the one of the plurality of user-specificstorages.
 22. A device comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the device to: determine a first portion of a content item in eachof a plurality of user-specific storages associated with correspondinguser accounts of a plurality of user accounts and determine a secondportion of the content item in a common storage associated with theplurality of user accounts; determine that one or more caching criteriais not satisfied for at least a portion of the stored content item;determine, based on the determining that one or more caching criteria isnot satisfied, to remove the second portion from cache storage differentfrom the common storage; cause, based on the determining to remove thesecond portion from the cache storage, the second portion to be removedfrom the cache storage different from the common storage; and causesending of a first portion from one of the plurality of user-specificstorages and the second portion from the common storage.
 23. The deviceof claim 22, wherein at least a portion of the content item is beingrecorded while the second portion is caused to be stored in the cachestorage.
 24. The device of claim 22, wherein the at least a portion ofthe stored content item is requested by at least a portion of users ofthe plurality of user accounts before the content item is finished beingrecorded.
 25. The device of claim 22, wherein the instructions, whenexecuted by the one or more processors, further cause the device tocount a number of the plurality of user accounts currently accessing atleast a portion of the content item and update, based on a change in thenumber, the caching criteria.
 26. The device of claim 22, wherein theone or more caching criteria comprises a range of a plurality ofsegments of the content item predicted to be accessed by at least aportion of the plurality of user accounts engaged in active playback ofthe content item.
 27. The device of claim 26, wherein the range isupdated over time to include subsequent segments of the content item asone or more of the plurality of user accounts progress in playback ofthe content item.
 28. The device of claim 26, wherein the range isassociated with timing information indicative of a length of time to usethe range for caching decisions.